Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

add configuration for eessi.io #206

Merged
merged 1 commit into from
Nov 16, 2023
Merged

Conversation

boegel
Copy link
Contributor

@boegel boegel commented Nov 13, 2023

After a lot of preparatory work, we now finally have a new CernVM-FS repository in place for the European Environment for Scientific Software Installations (EESSI), which is part of the effort to make EESSI ready for production that is funded via the MultiXscale EuroHPC Centre-of-Excellence.

The contents of this repository will gradually be expanded over the coming weeks/months/years via the semi-automated contribution workflow we have implemented and documented.
Later this year we would like to announce this repository as being the production-ready setup of EESSI.

It would be great to have this configuration be part of the default CernVM-FS configuration repository, especially since we will be using EESSI as a running example in the upcoming "Best Practices for CernVM-FS in HPC" tutorial.

cc @bedroge, @ocaisa, @casparvl, @trz42

Copy link
Collaborator

@DrDaveD DrDaveD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I suggest changing the key name to eessi.io.pub, so it implies that it applies to all repositories of the eessi.io domain. I know there's only one so far but there may be more in the future.

@boegel
Copy link
Contributor Author

boegel commented Nov 15, 2023

@DrDaveD If that's not required, I think we prefer to keep it as is for now, to leave the door open to use a different key per repository (unless that doesn't make much sense).

I guess we can easily change software.eessi.io.pub to eessi.io.pub later, or would that be a hassle?

Getting the configuration for software.eessi.io repository added is important for the upcoming tutorial, so we would prefer if that can be done quickly.

Copy link
Collaborator

@DrDaveD DrDaveD left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks good to me. It's up to @jblomer now to review, merge, and deploy.

After he has approved I'll also want a cherry-pick PR to the master branch. For egi and osg it probably requires a request from somebody in one of the supported VOs in those projects.

@DrDaveD DrDaveD requested a review from jblomer November 15, 2023 19:07
@jblomer jblomer requested a review from vvolkl November 16, 2023 10:11
@jblomer jblomer merged commit 566fa66 into cvmfs-contrib:default Nov 16, 2023
@boegel boegel deleted the eessi branch November 16, 2023 11:04
boegel added a commit to boegel/cvmfs-config-repo that referenced this pull request Nov 20, 2023
DrDaveD pushed a commit that referenced this pull request Nov 20, 2023
* add configuration for eessi.io (#206)

* include common.conf in config file for eessi.io (#207)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants